querify getting fake doc items - #161200
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
querify getting fake doc items
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (f21c600): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. @bors rollup=never rustc-perf Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.3%, secondary 0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.0%, secondary -6.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 455.832s -> 457.539s (0.37%) |
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
|
rustbot has assigned @dingxiangfei2009. Use Why was this reviewer chosen?The reviewer was selected based on:
|
2956a4e to
a46b0ca
Compare
|
r? @camelid |
|
r? compiler |
a46b0ca to
71584d5
Compare
This comment has been minimized.
This comment has been minimized.
|
Oh sorry for the review delay but I was actually reviewing this yesterday. I'll post a finished review asap. |
|
Oh sorry, I kinda glanced over the manual assignment 😳 |
| let features = tcx.features().enabled_features(); | ||
| if features.contains(&sym::rustc_attrs) || features.contains(&sym::rustdoc_internals) { | ||
| // Collect fake doc items in this crate. | ||
| for id in tcx.hir_root_module().item_ids { |
There was a problem hiding this comment.
It seems like this query now works for any item in the root, not just const items (like the old code) did. Is that intentional? We should probably restrict to just const _ items.
There was a problem hiding this comment.
It is still an error to put the attribute on something else, this doesn't matter for correctness.
Is that intentional?
Yes, what this code now does is check whether the attribute is on the item. What the old code did is perform a check for whether we should check for whether the attribute is on the item.
71584d5 to
72e0459
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@rustbot ready |
View all comments